|
factline made arrangements to assure
data to be stored confidentially and that persons have no access to
data they are not permitted for. Please extract an overview of the
marrow regulations referring to data security from the “Affix
factline data security”.
Data security in the ASP-model
A few concrete notes to the handling
on the ASP-server:
Backup frequency: Every 24 hours
a backup will be made from all data on the ASP-server and will
then be available for 7 days. Concretely, a dump will be taken
from the database and the files will be synchronised with 2
directories.
The backup-data will be copied
physically from the backup-server to another server every 24
hours. These data will be available for 7 days too.
Extended reliability: The server
uses RAID 1 (which means that two hard discs contain exactly the
same data – in the case one drops out, the other hard disc
assumes the operations automatically).
Data security on server solutions
Basically it is possible to stage a
server similarly as it was on the ASP-model. That ensures at least
the same standards. Occasionally it is possible to take exceeding
measures.
Conceivable extensions could be
Backups more frequently on the
local server: The data on the ASP-server will be saved once every
24 hours on a different server at the same host (Hetzner). On
demand the backup rate could be reduced. But it needs to be kept
in mind that this has an impact on the amount of days which
backups are available.
Longer preservation of
backup-copies: Before they will be overrode again the complete
backups will be kept for 7 days on the ASP-server. If once
detects a loss of data on day 8, it is not possible to reset the
data. (But that is, as far as our experience goes, unlikely.)
WORM storage: Optionally it
would be conceivable to transcend all generated data (facts and
log-data) to another place once every 24 hours and then to burn it
onto a single writeable medium (e.g. DVD) once a week.
Increased reliability: RAID1
will be applied for ASP-servers. To endow an own (decided) server
with an elevated RAID (e.g. RAID 5) would be imaginable.
Implementation of a secure and
encrypted connection: HTTPS is used for encryption and
communication-authentication between web-server and browser.
Without encryption IP-packages would be readable as plain text for
anyone who has according access to the net. It is important to
note that the data-transfer takes more time with HTTPS.
Costs for increased precaution will
be calculated with the arising expenses according to the current
factline price list for services. (see
http://www.factline.com/148782.0)
|
|